Log client addresses in scheduler lifecycle messages#9270
Conversation
Signed-off-by: peter941221 <peter941221@gmail.com>
Signed-off-by: peter941221 <peter941221@gmail.com>
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 40 files + 1 40 suites +1 14h 37m 47s ⏱️ + 1h 7m 32s For more details on these failures, see this check. Results for commit acf771d. ± Comparison against base commit 20d80c9. This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.This pull request skips 1 test.♻️ This comment has been updated with latest results. |
|
Current red jobs look unrelated to this patch. This PR only changes |
Summary
ClientStateso the same address is available throughout the client lifecycleCloses #8000
Testing
python -m py_compile distributed/scheduler.py distributed/tests/test_scheduler.pypython -m pytest distributed/tests/test_scheduler.py -k client_connection_logs_include_address(local environment is missingdask, so pytest fails during config import)